Fix investigation tour availability after organization loads - #2598
Merged
Merged
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
ejsmith
approved these changes
Sep 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix “Investigate an error” staying on its availability check after login. Track the caller’s enabled gate in the query-options factory while retaining the
enabledcallback and authentication/organization checks. Treat placeholder results as loading so the previous organization’s errors cannot temporarily enable the guide after switching organizations.@ejsmith please review. Diff: three added lines and two removed lines across two existing files.
Validation: frontend validation and all 10 existing host/catalog tests passed; the responsive/identity tour E2E passed. Agent Browser verified mobile Back/Next/completion, reload persistence, organization switching, lookup failure/recovery, and historical event/stack saved views.
Remaining gate: the local mobile investigation E2E fails during fixture setup because Elasticsearch refuses to allocate today’s event shard at 94% disk usage. Current-date queries return 500. Full CI must pass on the updated commit before release approval.